Cross sections format modification and EEDF solver correction - #2172

This Pull request follows three previous pull requests aiming at the improvement of the low temperature plasma modelling capabilities of Cantera.

The first pull request that proposed a lot of changes (#2121) was split in smaller pull requests, two of them which already got integrated:

#2144 addressed points 2, 3 and 4 of the original PR.
#2145 addressed points 6 and 7 of the original PR.

The present PR addresses the last two remaining points of the initial pull request:

1. Solved the EEDF computation issue: the solver now converges to the right EEDF. As you may have noticed, the example on the website gets the right trend but the values are off (figures 1a and 1c). This is because the effective cross-sections and elastic cross-sections were treated in the same way whereas they should not be: effective = elastic + inelastic. This ended up in counting the inelastic cross-sections twice, thus lowering the EEDF value on the high energies with respect to the correct solution. As can be seen on figure 1b and 1d, this is now fixed.

Running the same case as the Cantera example for some additional reduced electric fields yields a perfect agreement with BOLOS:

5. Implemented a new format for the YAML files avoiding information duplication but solving the current problem of cross-section datasets inconsistency, all the while keeping readability. Hopefully you will find it satisfactory. Here is its presentation:
   The idea of this YAML format for electron collision reactions is to separate the data needed for the chemical solver from the data needed for the EEDF solver, the ultimate goal being to allow for a minimal user error while manipulating the cross-section datasets (which remains as close as possible to the original LXcat reference). However, you made a good point in the previous discussions by stressing that the reactions should not duplicate information from the cross-sections. Therefore, now all the information is stored in the cross-sections, which are themselves all stored in the electron-collisions YAML node for safety and clarity purposes. To link the reactions involving electron collisions to their data, a field “name” was added to the cross-sections.
   This field is constructed from the cross-section data taken from the LXCat database as follows: databaseName_target_kind_product_threshold to create a unique identifier that is then declared in the appropriate reaction in the reaction YAML node if this reaction if wished by the user to be taken into account into the chemistry.

All relevant tests and documentation have been modified accordingly, so for further details you may also find useful to consult the updated documentation of this PR.

• Limited use of generative AI for the actual code itself and for documentation.
  Standard or boilerplate code snippets were generated with AI and manually reviewed;
  all design, logic, and implementation decisions were made by the contributor.
  Examples: IDE code-completions or brief LLM queries for common patterns.

• Extensive use of generative AI for the tests.
  Significant portions of code or documentation were generated with AI, including
  logic and implementation decisions. All generated code and documentation were
  reviewed and understood by the contributor. Examples: Output from agentic coding
  tools and/or substantial refactoring by LLMs (web-based or local).